Repository navigation
feat(docker): ship a Dockerfile Glama can build and introspect - #10
Merged
Merged
Conversation
Glama builds every server from a Dockerfile - maintainer-authored or inferred. The inferred build did not produce a working image, so the listing shows no tools and no deployable release. This one installs the package, keeps memory under /data and runs the stdio server as a non-root user.
Codex Review Summary: ✅ CompletedThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Glama builds every open-source server in its registry from a Dockerfile — the maintainer's if the repo carries one, otherwise an AI-inferred build. The inferred build for this repo does not produce a working image, so the listing currently shows no tools, cannot be deployed, and has no release. That is also what keeps the
missing-glamarequirement in awesome-mcp-servers from being meaningful.What this adds
Dockerfile—python:3.13-slim,libgomp1(onnxruntime through fastembed, pyarrow through lancedb),pip install .from the repo, memory under/data, non-root uid 1000,CMD ["turbo-memory-mcp", "serve"]..dockerignore— keeps.git, tests, benchmarks, docs, the demo mp4 and local venvs out of the build context (2.4 MB context instead of the whole repo).No port, no volume requirement: the server is stdio-only, an MCP client drives it.
VOLUME ["/data"]only marks where the memory lives if someone wants to persist it.Verification
No Docker daemon on this machine, so the build steps were reproduced exactly as the image runs them: the Docker context (tracked files, minus everything
.dockerignoreexcludes, plus the two new files — 86 files, 2.4 MB) was installed into a fresh Python 3.13 venv withpip install ., and the installed entry point was driven over stdio with a real MCPinitialize+tools/listexchange:All 29 tools come back with no network access, no model download and no credentials, which is what Glama's introspection asks for. The same probe against the working tree gave the same 29 tools in 3.3 s.
CI (lint + the 3.11/3.13/windows test matrix) runs on this PR; the Dockerfile itself does not touch the package, so a green run here plus the probe above is the evidence I can produce without a Docker host.